Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.57%. Comparing base (5d3344a) to head (15ca8ba).
Report is 5 commits behind head on main.

@@            Coverage Diff            @@
##               main    #2036   +/-   ##
=========================================
  Coverage     83.57%   83.57%           
  Complexity     2380     2380           
=========================================
  Files           235      235           
  Lines          7259     7259           
  Branches        382      382           
=========================================
  Hits           6067     6067           
  Misses          956      956           
  Partials        236      236           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Removing exceptions... I thought this was a binary breaking change, but the API checks didn't fail for this change...

I need to look at this further.

Do you want me to try and split this between main and test?

Also, I would think this would still be acceptable to do to non-public methods in main as users can't write code to link to them outside of reflection anyways.

Finally, can you also provide more information on this project's stance on binary breaking change? Is this project fully against them, or this requires a special release?

Also what checks is used to catch these? I see the POM has japicmp-maven-plugin.

Documentation:
https://docs.oracle.com/javase/specs/jls/se11/html/jls-13.html#jls-13.4.21 (Java 11 JLS)

Changes to the throws clause of methods or constructors do not break compatibility with pre-existing binaries; these clauses are checked only at compile time.

This says it is not a breaking binary change.

This section also hasn't changed up to JLS 22 ( https://docs.oracle.com/javase/specs/jls/se22/html/jls-13.html#jls-13.4.21 ).